Media capture lock affordance for graphical user interface

ABSTRACT

The disclosed embodiments are directed to a media capture lock affordance for a graphical user interface displayed by a media capture device. The media capture lock affordance allows a user to lock and unlock a capture state of the media capture device using a simple and intuitive touch gesture that can be applied by the user&#39;s finger (e.g., the user&#39;s thumb) while holding the media capture device in one hand.

CROSS-RELATED APPLICATION

This application claims the benefit of priority from U.S. ProvisionalPatent Application No. 62/628,825 for “Media Capture Lock Affordance forGraphical User Interface, filed Feb. 9, 2018, which provisional patentapplication is incorporated by reference herein in its entirety.

TECHNICAL FIELD

This disclosure relates generally to graphical user interfaces for mediacapture applications.

BACKGROUND

Media capture devices (e.g., smart phones, tablet computers), includeapplications that allow users to record media clips (e.g., video clips,audio clips) using one or more embedded cameras and microphones. Theuser holds down a virtual record button to capture a media clip. Oncethe user is done recording, the user can drag the media clip into adesired order with other media clips and add filters, emoji, animatedicons and titles. Media clips can be shared indirectly through socialnetworks and/or sent directly to friends through, for example, instantmessaging applications.

SUMMARY

The disclosed embodiments are directed to a media capture lockaffordance for a graphical user interface. In an embodiment, a method ofcapturing media comprising: detecting, by a media capture device, a tapand hold gesture input directed to a media capture affordance displayedat a first location on a graphical user interface presented on a displayscreen of the media capture device; responsive to the tap and holdgesture input, initiating, by the image capture device, a media capturesession on the media capture device in an unlocked state; responsive tothe media capture device detecting a first lift gesture in which the tapand hold gesture input lifts from the first location on the graphicaluser interface during the media capture session, terminating, by theimage capture device, the media capture session; responsive to the mediacapture device detecting a slide gesture input in which the mediacapture affordance slides from the first location to a second locationon the graphical user interface during the media capture session,changing, by the media capture device, the media capture affordance to amedia capture lock affordance; and responsive to the media capturedevice detecting a second lift gesture in which the slide gesture inputlifts from the graphical user interface at the second location duringthe media capture session, transitioning, by the media capture device,the media capture session into a locked state.

Other embodiments can include an apparatus, computing device andnon-transitory, computer-readable storage medium.

Particular embodiments disclosed herein may provide one or more of thefollowing advantages. A media capture lock affordance allows a user tolock and unlock a capture state of a media capture device using a simpleand intuitive touch gesture that can be applied by the user's finger(e.g., the user's thumb) while holding the media capture device in onehand.

The details of one or more implementations of the subject matter are setforth in the accompanying drawings and the description below. Otherfeatures, aspects and advantages of the subject matter will becomeapparent from the description, the drawings and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1H illustrate operation of a media capture lock affordance,according to an embodiment.

FIG. 2 is a flow diagram of an animation process for the media capturelock affordance shown in FIGS. 1A-1H, according to an embodiment.

FIG. 3 illustrates an example device architecture of a media capturedevice implementing the media capture lock affordance described inreference to FIGS. 1-2, according to an embodiment.

DETAILED DESCRIPTION Example Media Lock Affordance

This disclosure relates to media recording functionality of a mediacapture device that locks a media capture affordance on a graphical userinterface (GUI) into a locked media capture state for continuous mediacapture. In an embodiment, to initiate a media capture session of amedia clip (e.g., a video clip, audio clip), the user taps and holds themedia capture affordance (e.g., a virtual recording button). As long asthe user holds their touch on the media capture affordance, the mediacontinues to be captured by the media capture device. If the userremoves their touch during the media capture session, the media capturesession terminates. If the user maintains their touch on the mediacapture affordance while making a sliding gesture with their finger, themedia capture affordance visually changes to a locked media captureaffordance and the media capture session is maintained, resulting incontinuous recording of the media. In an embodiment, the locked mediacapture affordance moves down below the user's finger so that it is notobscured by the user's finger. The user can remove their finger from thelocked media capture affordance and the media capture session will bemaintained until the user taps the locked state capture button, whichthen terminates the media capture session.

FIGS. 1A-1H illustrate operation of a media capture lock affordance,according to an embodiment. Referring to FIG. 1A, media capture device100 is presenting GUI 101 on a display screen. GUI 101 includes mediacapture affordance 102. Media capture device 100 is shown in thisexample embodiment as a smartphone. Media capture device 100, however,can be any electronic device capable of capturing media, includingtablet computers, wearable computers, digital cameras, video recordersand audio recording devices. Media capture affordance 102 can have anydesired shape, size or color. In the example shown, media captureaffordance 102 is an oval shape button. GUI 101 also includes a displayarea for displaying live media and playing back captured media. Mediacan be any type of media that can be captured, including video, stillimages and audio or any combination thereof.

Referring to FIG. 1B, a user taps and holds 103 (shown as a dashedcircle) media capture affordance 102 with their finger (e.g., theirthumb while holding media capture device 100) to initiate a mediacapture session in an “unlocked” state. During the media capturesession, an embedded video camera and/or one or more microphones capturemedia (e.g., capture video and audio). The media capture session is“unlocked” meaning that if the user lifts their finger from mediacapture affordance 102 (lifts their finger off the display screen), themedia capture session terminates, and the media is stored on mediacapture device 100 (e.g., stored in cache memory). Visual directionindicator 104 a (e.g., an arrow head) is displayed on GUI 101 toindicate a direction in which the user may slide their finger totransition the media capture session into a “locked” state. While in the“locked” state, the media is continuously captured without interruption.For example, video and audio will continue to record and still imageswill be taken in “burst” mode. Text is also displayed on GUI 101 thatinstructs the user to “slide up for continuous recording.”

In some embodiments, additional affordances (not shown) are included onGUI 101 for allowing the user to playback the captured media(hereinafter also referred to as a “media clip”), and order, filter, addemoji, animated icons and titles to the media clip. Other affordancesallow the user to share the media clips indirectly with socialnetworking websites and directly with friends and family through variouscommunication means (e.g., instant messaging, email, tweeting). In theembodiment shown, a navigation bar is located under the media displayarea that allows the user select an operation mode such as Camera,Library and Posters.

Referring to FIG. 1C, shows the user's slide gesture input resulting inmedia capture affordance 102 sliding up toward the media capture area.Note that during a slide gesture input the user's finger does not breakcontact with the display screen.

Referring to FIGS. 1D-1G, when the user slide media capture affordance102 up a predetermined distance, media capture affordance 102 changes ormorphs into media capture lock affordance 105 to visually indicate a“locked” state, as shown in FIG. 1F. The text below the media displayarea also changes to instruct the user how to exit the “locked” statesuch as, for example, “tap to stop recording.” Media capture lockaffordance 105 can be any size, shape or color. In the example shown,media capture lock affordance 105 is a square button. After the changeor morph from media capture affordance 102 to media capture lockaffordance 105, if the user lifts their finger and breaks contact withthe display screen, the media capture session enters the “locked” state.In the “locked” state the media capture session continues with the mediacapture until the user taps 106 media capture lock affordance 105 (FIG.1G), in which case the media capture session terminates. In analternative embodiment, visual direction indicator 104 a can be replacedwith button track 104 b to show the user the distance the user shouldslide media capture affordance 102 to enter the “locked” state.

In other embodiments, multiple taps can be used instead of a single tap.The direction of the slide gesture input can be in any direction on GUI101, including up, down, right and left. A sound effect can be played insync with the tap and slide gesture, such as a “click” sound effect toindicate when the media capture session is locked and unlocked. In anembodiment, force feedback (e.g., a vibration) can be provided by ahaptic engine to indicate when the media capture session is locked andunlocked. Affordances 102, 106 can be placed at any desired location onGUI 101, and can change location, size and/or shape in response to theorientation of media capture device 100, such as portrait and landscapeorientations. In an embodiment, the user can enter or exit a lockedmedia capture state using a voice command, which is processed by aspeech detection/recognition engine implemented in media capture device100.

Example Processes

FIG. 2 is a flow diagram of an animation process for the media capturelock affordance shown in FIGS. 1A-1H, according to an embodiment.Process 200 can be implemented using the device architecture 300described in reference to FIG. 3.

Process 200 begins by receiving a tap and hold gesture input directed toa media capture affordance at a first location of a GUI presented on adisplay device of a media capture device (201). The media captureaffordance can be and size, shape or color. The first location can beany desired location on the GUI. Responsive to the tap and hold gestureinput, process 200 initiates a media capture session on the mediacapture device, where the media capture session is initiated in an“unlocked” state (202). Responsive to a first lift gesture at the firstlocation, process 200 terminates the media capture session (203).

Responsive to a slide gesture input from the first location to a secondlocation on the GUI, process 200 changes the media capture affordance toa media capture lock affordance (204). The media capture lock affordancecan be any size, shape or color. The second location can be any desiredlocation on the GUI except the first location. The slide gesture can bein any desired direction including up, down, left and right.

Responsive to detecting a second lift gesture at the second location,process 200 transitions the media capture session from an unlocked stateinto a locked state (205). In a locked state, the media capture devicewill capture media continuously, until the user taps the media capturelock affordance to terminate the media capture session. In anembodiment, the user can tap anywhere on the GUI to terminate the mediacapture session after the second lift gesture, or press a mechanicalbutton on the media capture device (e.g., a home button on asmartphone).

Exemplary Mobile Device Architecture

FIG. 3 illustrates an example media capture device architecture 300 of amobile device implementing the media capture lock affordance describedin reference to FIGS. 1 and 2. Architecture 300 can include memoryinterface 302, one or more data processors, image processors and/orprocessors 304 and peripherals interface 306. Memory interface 302, oneor more processors 304 and/or peripherals interface 306 can be separatecomponents or can be integrated in one or more integrated circuits. Thevarious components in architecture 300 can be coupled by one or morecommunication buses or signal lines.

Sensors, devices and subsystems can be coupled to peripherals interface306 to facilitate multiple functionalities. For example, one or moremotion sensors 310, light sensor 312 and proximity sensor 314 can becoupled to peripherals interface 306 to facilitate motion sensing (e.g.,acceleration, rotation rates), lighting and proximity functions of themobile device. Location processor 315 can be connected to peripheralsinterface 306 to provide geopositioning. In some implementations,location processor 315 can be a GNSS receiver, such as a GlobalPositioning System (GPS) receiver chip. Electronic magnetometer 316(e.g., an integrated circuit chip) can also be connected to peripheralsinterface 306 to provide data that can be used to determine thedirection of magnetic North. Electronic magnetometer 316 can providedata to an electronic compass application. Motion sensor(s) 310 caninclude one or more accelerometers and/or gyros configured to determinechange of speed and direction of movement of the mobile device.Barometer 317 can be configured to measure atmospheric pressure aroundthe mobile device.

Camera subsystem 320 and an optical sensor 322, e.g., a charged coupleddevice (CCD) or a complementary metal-oxide semiconductor (CMOS) opticalsensor, can be utilized to facilitate camera functions, such ascapturing photographs and recording video clips.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 324, which can include radio frequency (RF)receivers and transmitters (or transceivers) and/or optical (e.g.,infrared) receivers and transmitters. The specific design andimplementation of the communication subsystem 324 can depend on thecommunication network(s) over which a mobile device is intended tooperate. For example, architecture 300 can include communicationsubsystems 324 designed to operate over GSM networks, GPRS networks,EDGE networks, a Wi-Fi™ or Wi-Max™ networks and Bluetooth™ networks. Inparticular, the wireless communication subsystems 324 can includehosting protocols, such that the mobile device can be configured as abase station for other wireless devices.

Audio subsystem 326 can be coupled to a speaker 328 and a microphone 330to facilitate voice-enabled functions, such as voice recognition, voicereplication, digital recording and telephony functions. Audio subsystem326 can be configured to receive voice commands from the user.

I/O subsystem 340 can include touch surface controller 342 and/or otherinput controller(s) 344. Touch surface controller 342 can be coupled toa touch surface 346 or pad. Touch surface 346 and touch surfacecontroller 342 can, for example, detect contact and movement or breakthereof using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared and surfaceacoustic wave technologies, as well as other proximity sensor arrays orother elements for determining one or more points of contact with touchsurface 346. Touch surface 346 can include, for example, a touch screen.I/O subsystem 340 can include a haptic engine or device for providinghaptic feedback (e.g., vibration) in response to commands from aprocessor.

Other input controller(s) 344 can be coupled to other input/controldevices 348, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of speaker 328 and/or microphone 330. Touch surface 346 or othercontrollers 344 (e.g., a button) can include, or be coupled to,fingerprint identification circuitry for use with a fingerprintauthentication application to authenticate a user based on theirfingerprint(s).

In one implementation, a pressing of the button for a first duration maydisengage a lock of the touch surface 346; and a pressing of the buttonfor a second duration that is longer than the first duration may turnpower to the mobile device on or off. The user may be able to customizea functionality of one or more of the buttons. The touch surface 346can, for example, also be used to implement virtual or soft buttonsand/or a virtual touch keyboard.

In some implementations, the mobile device can present recorded audioand/or video files, such as MP3, AAC and MPEG files. In someimplementations, the mobile device can include the functionality of anMP3 player. Other input/output and control devices can also be used.

Memory interface 302 can be coupled to memory 350. Memory 350 caninclude high-speed random access memory and/or non-volatile memory, suchas one or more magnetic disk storage devices, one or more opticalstorage devices and/or flash memory (e.g., NAND, NOR). Memory 350 canstore operating system 352, such as iOS, Darwin, RTXC, LINUX, UNIX, OSX, WINDOWS, or an embedded operating system such as VxWorks. Operatingsystem 352 may include instructions for handling basic system servicesand for performing hardware dependent tasks. In some implementations,operating system 352 can include a kernel (e.g., UNIX kernel).

Memory 350 may also store communication instructions 354 to facilitatecommunicating with one or more additional devices, one or more computersand/or one or more servers, such as, for example, instructions forimplementing a software stack for wired or wireless communications withother devices. Memory 350 may include graphical user interfaceinstructions 356 to facilitate graphic user interface processingdescribed in reference to FIGS. 1 and 2; sensor processing instructions358 to facilitate sensor-related processing and functions; phoneinstructions 360 to facilitate phone-related processes and functions;electronic messaging instructions 362 to facilitate electronic-messagingrelated processes and functions; web browsing instructions 364 tofacilitate web browsing-related processes and functions; mediaprocessing instructions 366 to facilitate media processing-relatedprocesses and functions; GNSS/Location instructions 368 to facilitategeneric GNSS and location-related processes and instructions; camerainstructions 370 to facilitate camera-related processes and functionsdescribed in reference to FIGS. 1 and 2; and other application 372instructions. The memory 350 may also store other software instructions(not shown), such as security instructions, web video instructions tofacilitate web video-related processes and functions and/or web shoppinginstructions to facilitate web shopping-related processes and functions.In some implementations, the media processing instructions 366 aredivided into audio processing instructions and video processinginstructions to facilitate audio processing-related processes andfunctions and video processing-related processes and functions,respectively.

In an embodiment, the taps, slide and lift gestures described inreference to FIGS. 1 and 2 are detected using a touch event modelimplemented in software on media capture device 300. An example touchevent model is described in U.S. Pat. No. 8,560,975, entitled “TouchEvent Model,” issued on Oct. 15, 2013, which patent is incorporated byreference herein in its entirety.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. Memory 350 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the mobile device may be implemented in hardware and/or insoftware, including in one or more signal processing and/or applicationspecific integrated circuits.

The described features can be implemented advantageously in one or morecomputer programs that are executable on a programmable system includingat least one programmable processor coupled to receive data andinstructions from, and to transmit data and instructions to, a datastorage system, at least one input device, and at least one outputdevice. A computer program is a set of instructions that can be used,directly or indirectly, in a computer to perform a certain activity orbring about a certain result. A computer program can be written in anyform of programming language (e.g., SWIFT, Objective-C, C#, Java),including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, component,subroutine, a browser-based web application, or other unit suitable foruse in a computing environment.

Suitable processors for the execution of a program of instructionsinclude, by way of example, both general and special purposemicroprocessors, and the sole processor or one of multiple processors orcores, of any kind of computer. Generally, a processor will receiveinstructions and data from a read-only memory or a random-access memoryor both. The essential elements of a computer are a processor forexecuting instructions and one or more memories for storing instructionsand data. Generally, a computer will also include, or be operativelycoupled to communicate with, one or more mass storage devices forstoring data files; such devices include magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; andoptical disks. Storage devices suitable for tangibly embodying computerprogram instructions and data include all forms of non-volatile memory,including by way of example semiconductor memory devices, such as EPROM,EEPROM, and flash memory devices; magnetic disks such as internal harddisks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, ASICs (application-specific integrated circuits).

To provide for interaction with a user, the features can be implementedon a computer having a display device such as a CRT (cathode ray tube)or LCD (liquid crystal display) monitor or a retina display device fordisplaying information to the user. The computer can have a touchsurface input device (e.g., a touch screen) or a keyboard and a pointingdevice such as a mouse or a trackball by which the user can provideinput to the computer. The computer can have a voice input device forreceiving voice commands from the user.

The features can be implemented in a computer system that includes aback-end component, such as a data server, or that includes a middlewarecomponent, such as an application server or an Internet server, or thatincludes a front-end component, such as a client computer having agraphical user interface or an Internet browser, or any combination ofthem. The components of the system can be connected by any form ormedium of digital data communication such as a communication network.Examples of communication networks include, e.g., a LAN, a WAN, and thecomputers and networks forming the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits data (e.g., an HTML page) to a clientdevice (e.g., for purposes of displaying data to and receiving userinput from a user interacting with the client device). Data generated atthe client device (e.g., a result of the user interaction) can bereceived from the client device at the server.

A system of one or more computers can be configured to performparticular actions by virtue of having software, firmware, hardware, ora combination of them installed on the system that in operation causesor cause the system to perform the actions. One or more computerprograms can be configured to perform particular actions by virtue ofincluding instructions that, when executed by data processing apparatus,cause the apparatus to perform the actions.

One or more features or steps of the disclosed embodiments may beimplemented using an Application Programming Interface (API). An API maydefine on or more parameters that are passed between a callingapplication and other software code (e.g., an operating system, libraryroutine, function) that provides a service, that provides data, or thatperforms an operation or a computation. The API may be implemented asone or more calls in program code that send or receive one or moreparameters through a parameter list or other structure based on a callconvention defined in an API specification document. A parameter may bea constant, a key, a data structure, an object, an object class, avariable, a data type, a pointer, an array, a list, or another call. APIcalls and parameters may be implemented in any programming language. Theprogramming language may define the vocabulary and calling conventionthat a programmer will employ to access functions supporting the API. Insome implementations, an API call may report to an application thecapabilities of a device running the application, such as inputcapability, output capability, processing capability, power capability,communications capability, etc.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as descriptions offeatures specific to particular embodiments of particular inventions.Certain features that are described in this specification in the contextof separate embodiments can also be implemented in combination in asingle embodiment. Conversely, various features that are described inthe context of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to a subcombination or variation of a sub combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

What is claimed is:
 1. A method of capturing media comprising:detecting, by a media capture device, a tap and hold gesture inputdirected to a media capture affordance displayed at a first location ona graphical user interface presented on a display screen of the mediacapture device; responsive to the tap and hold gesture input,initiating, by the image capture device, a media capture session on themedia capture device in an unlocked media capture session state;responsive to the media capture device detecting a first lift gesture inwhich the tap and hold gesture input lifts from the first location onthe graphical user interface during the media capture session,terminating, by the image capture device, the media capture session;responsive to the media capture device detecting a slide gesture inputin which the media capture affordance slides from the first location toa second location on the graphical user interface during the mediacapture session, changing, by the media capture device, the mediacapture affordance to a media capture lock affordance; and responsive tothe media capture device detecting a second lift gesture in which theslide gesture input lifts from the graphical user interface at thesecond location during the media capture session, transitioning, by themedia capture device, the media capture session into a locked mediacapture session state.
 2. The method of claim 1, wherein: responsive toa tap gesture input directed to the media capture lock affordance,terminating the locked state or media capture session.
 3. The method ofclaim 1, wherein changing the media capture affordance to the mediacapture lock affordance includes changing a size of the media captureaffordance.
 4. The method of claim 1, wherein changing the media captureaffordance to the media capture lock affordance includes changing thesize and a shape of the media capture affordance.
 5. The method of claim1, wherein changing the media capture affordance to the media capturelock affordance includes animating the media capture affordance to morphinto the media capture lock affordance.
 6. The method of claim 1,further comprising: causing to display on the GUI a visual indicatorindicating a direction for the slide gesture input on the GUI.
 7. Themethod of claim 1, further comprising: causing to display a first textmessage on the GUI before the slide gesture input, and displaying asecond text message, different than the first text message, after thesecond lift gesture.
 8. A media capture device comprising: a touchscreen; one or more processors; memory coupled to the one or moreprocessors and configured to store instructions, which, when executed bythe one or more processors, cause the one or more processors to performoperations comprising: detecting, by the touch screen, a tap and holdgesture input directed to a media capture affordance displayed at afirst location on a graphical user interface presented on the touchscreen of the media capture device; responsive to the tap and holdgesture input, initiating a media capture session on the media capturedevice in an unlocked media capture session state; responsive to thetouch screen detecting a first lift gesture in which the tap and holdgesture input lifts from the first location on the graphical userinterface during the media capture session, terminating the mediacapture session; responsive to the touch screen detecting a slidegesture input in which the media capture affordance slides from thefirst location to a second location on the graphical user interfaceduring the media capture session, changing the media capture affordanceto a media capture lock affordance; and responsive to the touch screendetecting a second lift gesture in which the slide gesture input liftsfrom the graphical user interface at the second location during themedia capture session, transitioning the media capture session into alocked media capture session state.
 9. The media capture device of claim8, wherein: responsive to a tap gesture input directed to the mediacapture lock affordance, terminating the locked media capture sessionstate.
 10. The media capture device of claim 8, wherein changing themedia capture affordance to the media capture lock affordance includeschanging an appearance of the media capture affordance.
 11. The mediacapture device of claim 8, wherein changing the media capture affordanceto the media capture lock affordance includes changing the size and ashape of the media capture affordance.
 12. The media capture device ofclaim 8, wherein changing the media capture affordance to the mediacapture lock affordance includes animating the media capture affordanceto morph into the media capture lock affordance.
 13. The media capturedevice of claim 8, the operations further comprising: causing to displayon the GUI a visual indicator indicating a direction for the slidegesture input on the GUI.
 14. The media capture device of claim 8, theoperations further comprising: causing to display a first text messageon the GUI before the slide gesture input, and displaying a second textmessage, different than the first text message, after the second liftgesture.
 15. A non-transitory, computer-readable storage medium havinginstructions stored thereon that when executed by a media capturedevice, causes the media capture device to perform operationscomprising: detecting, by the media capture device, a tap and holdgesture input directed to a media capture affordance displayed at afirst location on a graphical user interface presented on a displayscreen of the media capture device; responsive to the tap and holdgesture input, initiating, by the image capture device, a media capturesession on the media capture device in an unlocked media session capturestate; responsive to the media capture device detecting a first liftgesture in which the tap and hold gesture input lifts from the firstlocation on the graphical user interface during the media capturesession, terminating, by the image capture device, the media capturesession; responsive to the media capture device detecting a slidegesture input in which the media capture affordance slides from thefirst location to a second location on the graphical user interfaceduring the media capture session, changing, by the media capture device,the media capture affordance to a media capture lock affordance; andresponsive to the media capture device detecting a second lift gesturein which the slide gesture input lifts from the graphical user interfaceat the second location during the media capture session, transitioning,by the media capture device, the media capture session into a lockedmedia capture session state.
 16. The non-transitory, computer-readablestorage medium of claim 15, wherein: responsive to a tap gesture inputdirected to the media capture lock affordance, terminating the lockedstate or media capture session.
 17. The non-transitory,computer-readable storage medium of claim 15, wherein changing the mediacapture affordance to the media capture lock affordance includeschanging an appearance of the media capture affordance.
 18. Thenon-transitory, computer-readable storage medium of claim 15, whereinchanging the media capture affordance to the media capture lockaffordance includes animating the media capture affordance to morph intothe media capture lock affordance.
 19. The non-transitory,computer-readable storage medium of claim 15, further comprising:causing to display on the GUI a visual indicator indicating a directionfor the slide gesture input on the GUI.
 20. The non-transitory,computer-readable storage medium of claim 15, further comprising:causing to display a first text message on the GUI before the slidegesture input, and displaying a second text message, different than thefirst text message, after the second lift gesture.